docs(mesh): same-namespace consumer precedence#5282
Merged
Conversation
Document that a consumer default in the same namespace can override a producer policy for a specific service. Signed-off-by: slonka <slonka@users.noreply.github.com>
✅ Deploy Preview for kongdeveloper ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
The navtabs block requires a tab_group argument. Signed-off-by: slonka <slonka@users.noreply.github.com>
Automaat
approved these changes
May 19, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Ports the “same-namespace consumer default can override producer policy” nuance from kuma-website into the Mesh policy introduction doc, so Kubernetes users understand why a producer policy may not win when a consumer default exists in the same namespace.
Changes:
- Adds a superscript cross-link from the Producer policies section to the new exception note.
- Adds a new “Same-namespace exception” subsection under policy ordering, including tabbed YAML examples and mitigation guidance.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Contributor
Author
|
@lmilan - I've updated the branch so that CI kicks again. Could you review this and get this merged if everything is ok? |
Contributor
|
@slonka I reviewed this and made some changes:
Can you take a look and let me know what you think? Thanks! |
Contributor
Author
|
@lmilan looks better, thanks! can you approve this one and merge it? |
lmilan
approved these changes
May 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
preview: https://deploy-preview-5282--kongdeveloper.netlify.app/mesh/policies-introduction/#same-namespace-exception
fix: kumahq/kuma#13576
On Kubernetes, a consumer default in the same namespace can still override a producer policy for a specific service because policy role is evaluated before
spec.to[].targetRefspecificity. The kuma-website docs picked this up but pages under_src/policies/are no longer auto-synced to developer.konghq.com, so the same note has to be ported by hand toapp/mesh/policies-introduction.md.Implementation information
<sup>note</sup>link from the producer-policies paragraph to the new section.Same-namespace exceptionsection under policy ordering withProducer/Consumer default/Updated consumer policynavtabs and a short fix-it paragraph.Supporting documentation